home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
The 640 MEG Shareware Studio 2
/
The 640 Meg Shareware Studio CD-ROM Volume II (Data Express)(1993).ISO
/
mail
/
1st_101a.zip
/
WHATS.NEW
< prev
Wrap
Text File
|
1992-09-28
|
47KB
|
903 lines
This file documents changes made in 1stReader since the original
release. If you are reading this file from inside 1stReader you
can print this file to your printer. Just press the [ALT] and
the [P] keys together (make sure your printer is ready to
print).
New features in 1.01 09-28-92
────────────────────────────────────────────────────────────────
1. If you quote text from an ANSI message, as long as the
line quoted does not contain any ANSI sequences
itself, then 1stReader will apply the quote
marks to the message.
Thanks John Phillips
2. If 1stReader detects that the message is a Usenet
sourced message then 1stReader ALWAYS displays
it as a text message even if escape characters
are found in the message.
3. You can now press CTRL+ENTER to skip to the next thread
when you are reading messages in order by
thread.
4. I added one feature, but one that will address Joe
Roseman's concerns about the use of option # 17
in The Qmail Door (which limits conferences in
the packets to those scanned by the door instead
of every one of them).
The "Print" button in the "Join Conferences"
screen is still there, and it will be changed to
read "Conf List" at release time, but for now
it's function has changed, a bit.
When you select this button 1stReader looks to
the BBS subdirectory to see if "CNAMES.LST"
exists. If this file exists then 1stReader will
display it to the user (of course, they can
print it too by using ALT+P). After viewing
this list they will still be asked if they wish
to print the list of conferences on the printer.
The beauty behind this idea is that users can
turn on option #17 and download only the
conferences they have selected, but when it
comes time to add a new conference, they can
scan the list CNAMES.LST, find the conference,
and then add it manually.
It's much more efficient since sysops can
include CNAMES.LST in the .BBS file *AND* they
can customize it to fit their own needs. Also,
1ST-TIME.ZIP's function will be changed so that
it will always be sent to the user if new since
their last call (and option #21 is turned ON in
the door).
Joe was complaining that turning option #17 ON
would mean users wouldn't know which conferences
are available. Also, his system has 3,650
conferences and those were passed to the user
EACH time they used the door. This feature
removes that need and lets the sysop create
CNAMES.LST so conferences are grouped by topic
and network.
5. Added support for $$SPELL.BAT. I know I said no new
features for 1.01 but I've seen a bunch of
people asking for this one. If you have
$$SPELL.BAT in your BBS or SYSTEM subdirectory,
when you save a message, 1stReader will run the
batch file and process the message. It will
ask you if you wish to check spelling first.
My $$SPELL.BAT works with Sharespell and looks
like this:
@ECHO OFF
C:
CD \SYSTEM\SS23B
SS %1
6. Added a timeout counter in the script section. If
you get hung up on a prompt 1stReader will send
CRs in an attempt to locate itself. If 1st
sends FIVE CRs and it still cannot find itself
then it terminates the script.
7. Added support for the ABORT command in the script
language. This lets you change the number of
CRs required to abort a script.
8. Added a new script command. CAPTURE [ON|OFF] will turn
on a QWKID.CAP file capture of the
telecommunications session.
Thanks John Phillips
9. If you have more than a screenful's worth of .CMD or .LST
entries, the reader now shows characters at the
bottom of the box.
Thanks John Phillips
10. If the user is a novice (expert features is not turned
ON) and you add or edit a system, the reader
will pause two seconds after displaying the
system screen and then show the user online
help.
11. Added support for the "{" character in the modem init
fields. This character gets translated into a
carriage return.
12. Added support for the #FIRST@ variable inside scripts.
13. Removed the file import manager in the internal editor
and instead 1stReader now calls the full file
manager. I wrote the smaller import manager
before the full manager was written. Now, you
can use it to select a file and then press the
ENTER key. You'll be asked if you want to
import the selected file.
14. Any sysop can create a tutorial package for their own
BBS if they make the user's name "NEW USER" in
the packet and is named <BBSID>.QTU. 1stReader
will then treat the packet as a tutorial:
No bookmark is maintained
Messages are not sorted in any order
Due to a feature in Qmail Door, any
message left by "NEW USER" is
automatically changed to the user's
own login name when uploaded.
15. Added support for the batch file $$CNAMES.BAT. If you
click on the "Conf List" button while joining
conferences and $$CNAMES.BAT exists, 1stReader
will shell and execute this batch file. It
allows you, as sysop, to create a database
system for your conferences if you wish. Some
BBS' out there have over 5,000 conferences so
this is one way to manage that size system.
Thanks Richard Strang
16. Added support for the SERVICES.NEW file to be included
inside the QWK packet. When you select services
from the menu and this file is found in the WORK
area, it will be displayed to the user. The
idea here is to provide an 'introduction' into
services from the sysop.
17. 1st allows UPPER and lower case values for Logins and
Passwords for those systems that distinguish
between them (like TBBS).
18. Added support for the @variable #U-REPLY-TO@. If this
field is found in a Usenet sourced message then
the @variable contains this entry, otherwise it
defaults to the #U-FROM@ field.
NOTE! Because of this addition API$(70) used
to support the current conference name. This
has been moved to API$(84).
19. If 1stReader cannot locate 1ST.SET then it will
automatically create it.
20. Added support for @variable #API$(99). If you are
reading a message that contains " * Origin:" as
the tagline it will search for a valid FidoNet
address and place it in #API$(99).
21. You can now create $$ZIP.BAT files and use them when
managing files. If you click on a ZIP file then
$$ZIP.BAT is executed - it can be used to call
up SHEZ or any other program you wish.
Thanks John Phillips
22. 1stReader now shows dots besides the selected button.
Some users have said it is hard to distinguish
which button was the default button. Now,
1stReader places dots besides the default
button.
Thank Bill Bentley
23. Added support for the SCRIPTS subdirectory in 1stReader.
This subdirectory contains all of the .CMD, .LST
and .SCR files, making it easy to move a set of
files from one computer to another. 1stReader
will still locate files in the current
subdirectory too.
24. Added support for the @SWITCH(xx) variable. The "xx"
corresponds with the switches in the 'Setup'
section - there are 24 switches numbered from
the first one (Advanced features) to the 24th
switch (Internal packing).
You can use this variable in DOS commands and if
the switch is turned ON the string will be
replaced with a '-1'. Otherwise, the string
will be replaced with a '0' to indicate that the
switch is turned OFF.
25. Added support for $$Fxx.BAT files where 'xx' is
1 through 10. These correspond to the F1
through F10 function keys. If you press the
SHIFT+Fxx keys together then 1stReader will
execute this batch file. The file can either
reside in the BBS subdirectory or the system
subdirectory. Great for 'quick acting' programs
you do not want to place in the F7 pulldown
menus.
26. Added support for the MESSAGE.$$$ file. If you shell to
DOS while reading a mail packet, 1stReader now
checks to see if a file named MESSAGE.$$$ is in
the current subdirectory upon returning back
from the shell. If this file is found then it
will be read and the text will be inserted into
a reply message.
Why support this file? Let's say a company
wants to write a program that accepts input from
the 1stReader user but formats it into specific
fields. Instead of relying on the user to line
up the columns correctly, the program accepts
the input and fields the responses correctly.
When returning back to 1stReader it will check
for MESSAGE.$$$ and if found, read it and create
a reply containing the data.
The first few lines of MESSAGE.$$$ contains this
information about the message:
Conference number
Public or Personal message?
Message TO field
Subject field
Tagline
...message text follows...
If the "Public or Personal message?" line is
blank the message is a public message. If any
data is written to this line then the message is
a private message.
27. If the "Advanced Features" switch is turned OFF then
1stReader now ALWAYS returns to the mail packet
screen after exiting a mail packet. That way,
you can click on "MAIL" to send replies.
Previous versions of 1stReader would return you
back to the opening screen if no mail packets
were available after exiting a packet.
Thanks Don Presten
28. Added support for "x-SETUP". This file is intended to
be a text file where "x" is the system type as
defined in the 08-28 release. This file is
displayed to the user whenever a new BBS is
added to 1stReader. The file should explain to
the user what steps they need to perform before
1stReader is ready for use with the system.
For example, the user added a Wildcat! system to
the dialing directory then 30-SETUP would tell
the user that they must first manually call the
BBS and configure the Tomcat door before using
1stReader.
29. Added support for the #CLREOL@ variable used in PCBoard.
Also added support for #X00 and #XFF used in
PCBoard.
30. Added support for a new script function "KEYSTROKE=".
You can now test to see what keystroke was
entered at a PAUSE command, like this:
PAUSE
IF KEYSTROKE=27 GOTO xxxx ' ESC
IF KEYSTROKE=32 GOTO xxxx ' Space
Keystroke returns the ASCII value of the key
that was pressed at a PAUSE prompt. Lower case
values are automatically converted into upper
case.
31. If you are in novice mode and have entered replies for
a system in the reader, when you exit the
reader, 1st will ask you if you wish to receive
new mail immediately.
Thanks Don Presten
32. Added support for different bulletin board systems in
the script files. There is now a new entry in
the BBS system screen named "System type".
1stReader assigns these values to systems:
1 PCBoard/Qmail Door
2 PCBoard/MarkMail
3 PCBoard/Kmail
4 PCBoard/CamMail
5 PCBoard/Rosemail
30 Wildcat!
50 Maximus
If you selected "30" for a Wildcat system then
1stReader will look for the files named
30-MAIL.SCR, 30-REPLY.SCR and 30-CALL.SCR.
If these files were not found then 1stReader
reverts back to $$MAIL.SCR, $$REPLY.SCR and
$$CALL.SCR.
33. Added another new field in the BBS system screen named
"FIDO tags (Y/N)?". If set to "Y" then
1stReader will automatically leave FIDO
compatible taglines even if you have not turned
the FIDO switch ON in Setup's switches.
34. Added support for a new script command "TRANSMIT;".
This command works just like "TRANSMIT" except
that it converts all spaces into semi-colons.
35. Added support for .TMP (template) files. When you enter
a new message in the reader 1st looks for a
<conf name>.TMP file in either the BBS or system
subdirectory. If the file is not found then
1stReader looks for $$1ST.TMP in the BBS or
system subdirectories.
The idea behind this feature is to provide a
'template' that users can fill out for customer
service reports.
36. The reader now positions a block besides the NEWS, FILES
and SERVICES buttons in the 'Read messages'
screen if new bulletins, files or services were
included in the packet.
37. Starting with this release 1stReader will rezip mail
packets to keep the bookmark pointers if you are
reading a mail packet that was not created by
Qmail Door and option #21 turned on. This saves
the read flags from session to session, just
like DeLuxe² does.
Thanks Dan Snapper
38. 1stReader now stores your ZIPPY scan parameters for
each BBS. This means that you can have one set
of search parameters for BBS #1 and a totally
different set for BBS #2.
39. If you are using serial port #3 or serial port #4 with
1stReader then please use the "Setup" command
and select "Comm" from the menu. Change your
serial port entry to either a "3" or a "4".
This release of 1stReader changes the way we
address COM3 and COM4. If you do not do this
your reader may not be able to communicate with
your modem.
If you are using a non-standard IRQ and Base
address for your serial port, the format has
been changed to "Base,IRQ" where BASE is in
hexadecimal.
40. If you were using COM3 or COM4 and had passed along
the base address and IRQ values in the serial
port setup (in other words, used 4 3/2E8 for
serial port #4) then QSZ nor would DSZ work.
This release fixes this problem. Also, if you
wish to define your own base address and IRQ
values for your serial port, simply use
"IRQ,Base" (Example: 2E8,3) instead of the
"Port IRQ/Base" method. (Example: 4 3/2E8).
Thanks Michael Leavitt
41. This release of 1stReader can now pass the base address
and IRQ to QSZ/DSZ using the %4 DOS command
line variable. Use this option if your system
uses non-standard serial port addresses.
42. A new QSZ.EXE has been provided that supports the
"portx=" option. This lets you use
'nonstandard' serial ports with QSZ.
Thanks Rob Kittredge
43. QSZ now ALWAYS sets itself to 8 bit word, 1 stop bit
and NO parity. Some users have been reporting
that QSZ shifts into 7 bit operations. This
should fix that problem.
44. Added support for the $$DIAL.SCR script file. If this
file exists then 1stReader will use it to dial
the bulletin board system rather than using the
internal dialer. This lets you setup scripts to
call long distance access numbers like Sprint.
For example, my $$DIAL.SCR lets me access my
Sprint service in this manner:
TRANSMIT "ATDT 1-800-877-8000;^M"
WAITFOR "OK"
PAUSE 10
TRANSMIT "ATDT @PHONE@;^M"
WAITFOR "OK"
PAUSE 20
TRANSMIT "ATDT aaa bbb cccc dddd^M"
WAITFOR "CONNECT|BUSY|NO CARRIER"
The @variable @PHONE@ will be replaced with the
telephone number. And you MUST place:
WAITFOR "CONNECT|BUSY|NO CARRIER"
as the last line of your script. Now you can
setup 1stReader to dial a BBS in any manner
you may require.
Thanks Ed Shoulta
45. Added a .5 second pause after a DOS shell to QSZ so
DTR is given a chance to come back up. This
prevents systems from dropping scripts
immediately after a shell.
Thanks Scott Baker
46. When you are using the internal archiver the screen now
displays the amount of free memory available
while it performs the task.
Thanks Lou Kairys
47. Added support for $$REPLIES.BAT. This batch is to be
executed immediately after the .REP packet is
unpacked.
48. Added support for the PLAY script command. If the
ANSI Music switch is turned ON then the PLAY
command lets you play ANSI music in a script.
Syntax: PLAY <string>.
49. Added a counter at the top of the internal editor that
tells you the current line number the cursor is
selecting.
Features fixed in 1.01
──────────────────────
1. The reader now checks to make sure you have enough
free memory available before loading taglines
when you are saving messages. Otherwise, the
reader could clobber your taglines.
Thanks David Pottier
2. If you had no taglines or ONE tagline on file and
you also had 'randomized tags' turned ON then
the reader would hang forever when trying to
find a randomized tagline. Fixed!
Thanks Peter Svensson
3. If you twitted someone and you joined a conference that
only contained a message from that user, 1st
would get locked up. Fixed.
Thanks John Phillips
4. Added a .5 second delay to the dialing command before
it attempts to call the system. Just in case
the modem hasn't come up yet to DTR ready. This
fixes a problem where the modem would not dial a
number after the first dialing attempt.
Thanks Rob Kittredge
5. Added a .25 second delay between characters when sending
the dialing commands. This helps transmitting
dialing sequences.
Thanks Rob Kittredge
6. If you were in the external editor (in this case, QEdit)
and shelled to DOS from it, the screen would be
red and you couldn't type anything. This
happened because 1stReader wasn't clearing the
screen first. Fixed.
Thanks John Phillips
7. If you deleted a folder the screen display was messed
up. Fixed.
Thanks John Phillips
8. The reader would display a "More (Y/n)?" on some screens
when a CLS instruction was not the first line of
the file. Fixed.
Thanks John Phillips
9. The external archive routines could not create the
ORDER.ZIP file when you tried to enter an order.
Fixed.
10. The reader wouldn't quote the first line in a message
if you used an external editor. Fixed.
Thanks John Phillips
11. The #CONF@ variable would mess up the translation of
"."'s and " " characters. Fixed.
Thanks John Phillips
12. The reader now correctly keeps a tagline when you invoke
the OOPS button.
Thanks John Phillips
13. If you were using an external editor and had to 'Oops'
back into it when entering a message, you would
have to select 'Oops" again to get back to the
editor. Fixed.
Thanks John Phillips
14. If you had turned of the reader's ability to use DTR
to hang up the phone and had to terminate a call
to a BBS *before* connection was established the
reader would still try and send the ATH command.
Fixed.
Thanks John Phillips
15. If you used .CMD files for the editor or lister and
tried to use them while managing files while
reading a mail packet, the .CMD files couldn't
be found. Fixed.
Thanks John Phillips
16. The mouse buttons were inverted in the PACK screen.
I'm not including a new 1ST.CLR in the files
tonight, just mentioning the fix here.
Thanks John Phillips
17. The PCRelay routing would be fooled if "-> " was the
first item in the message. Fixed.
18. Users were entering QWKID's (such as "ALS.QWK") and of
course this would cause problems. 1st now strips
anything after a "." in the ID field.
19. The reader now CHDIRs into the same subdirectory you
are going to use to upload or download a file.
20. The reader would always write a HEADER even if you were
entering a new message. Fixed.
21. You can now use the TAB key to move between fields in
all of the screens. SHIFT+TAB works like the
UP arrow key.
Thanks Dan Moore
22. If you were in the "News" section and used the mouse
to click on "Quit" the system would really
lockup. Fixed.
Thanks John Phillips
23. If you selected a tagline from the .LST files you would
still be asked if you wished to save the
tagline. Fixed.
Thanks John Phillips
24. Broke the ability to flag multiple messages into the
file folders. Fixed.
25. When viewing ANSI files the reader now pauses before
hitting any clear screen codes. Makes it easier
to view them.
26. If the reader couldn't locate 1STTEXT then it would
create a whole host of problems. The reader now
gracefully exits displaying an error message.
Thanks David Pottier
27. If there was a zero byte SYSTEMS.DAT file on file
then the reader would lock up. Fixed.
28. Reply to a message, save reply to folder, press F10
and the next message appears but with colors
all messed up. Lockup. Fixed!
Thanks John Phillips
29. If you re-edit a message 1st now retains the same
tagline used earlier.
Thanks John Phillips
30. How this got by I'll never know the but the "Msg read"
indicator has been backwards since day one.
Fixed.
31. FINALLY! We've fixed the lockup problems experienced
when logging into systems. It indeed did
depend on shadowing video ROM and happened
because I was wrapping the FillScrn() routine
from line 26 (which doesn't exist) to line 24.
Blows up everything. Fixed.
Thanks Edward Greene
32. When you connected to a system using the scripts you
would see a "[0;37;40m" on the screen for a
split second. Fixed.
33. If you used the "Unpack" option in the file manager
and changed the directory name it was unpacking
to, 1stReader would ask you if you wished to
delete the contents of another area. Fixed.
Also, when unpacking the file, the reader would
place the files in the wrong area because it
missed a trailing "\". Fixed.
Thanks Rick Welshans
34. In ZIPPY scans, the reader would scan messages you had
read, even though you told the system to ignore
them. Fixed.
35. If you entered messages without a packet on file then
1stReader would not display the amount of free
memory available in the "Read messages" screen.
Fixed.
Thanks Greg Watson
36. The "FILE=<filespec>" feature worked in the signature
field as long as you didn't use a .LST
extension. This called up a picklist instead.
However, starting with this release you must use
a "SIG=<filespec>" to call up a signature file.
That way, we can have multiple signatures stored
in a picklist, and you can access the picklist
by using "SIGS.LST" as your signature in the
EDITORS area.
Works like this:
1) Go into Setups' EDITORS
2) Enter "SIGS.LST" as your signature
3) Press ENTER
4) Arrow up back to the signature field.
5) Press ALT+F8 to edit SIGS.LST
6) Make entry one "SIG=NAME1"
7) Make entry two "SIG=NAME2"
8) Make entry three "<your name>"
9) Save and exit
If NAME1 and NAME2 exist, then you can select
them for your signatures. Otherwise, you can
select "<your name>" and just get "your name".
37. Hmmm, found a situation where, when using CTRL+T to
move by word, where a bad variable name was
used. Fixed.
38. Changed the order used to release memory segments when
exiting a mail packet. It seems *most* of the
internal packing errors happen on exit so I've
changed the code to deallocate all of the
segments before creating the .REP.
39. If you saved a reply that was broken up into seperate
messages then the message count would always
be "1" in the right side of the subject.
1stReader should increment them as 1,2,3 etc.
Fixed.
40. If you used external editors, specifically using a .CMD
file to support more than one editor, and you
used the OOPS button to return back to the
editor, 1stReader would loose the filenames for
the ORIGINAL and REPLY filespecs. Fixed.
41. If you were in a popup .CMD file and pressed the ESC key
and then tried to shell to DOS using F5, you
couldn't do it. Fixed.
42. If you used the "DOOR" area and tried to RESET a
conference the display would mess up pretty
good. Fixed.
43. If you unpacked a .BBS file that contains a $$CALL
screen but NOT a READ.ME then the screen
would get messed up. Fixed.
44. If you used the "DOOR" section to ADD a conference
the message created would contain text on the
end of the "ADD" command. Fixed.
Thanks Greg Watson
45. If you entered "1800" (a time without a colon seperator)
for a start time to call a system 1stReader
wouldn't accept it. Fixed.
46. If the sysop included a 1ST-TIME.ZIP file inside the
mail packet then not only does 1stReader
automatically install it but it will display a
file named 1ST-TIME.NEW to the user so they will
know what has been added by the sysop.
47. If you re-edited a message in 1stReader then the reader
would loose the "Reference" number in the edited
message. Fixed.
Thanks Greg Watson
48. If you went into a system without a mail packet on file
and selected "DOOR", then tried to add a new
conference to your setup, the system would lock
up tight and draw vertical lines on the screen
(shades of Dave Nimon!). Fixed.
Thanks Greg Watson
49. If you used FILE= in a picklist and the file was not
on file, you'd lockup and get a QEMM error.
Fixed.
Thanks Greg Watson
50. When calling the online order system, the dialing number
would 'scroll' down through the display if the
number was busy. Fixed.
51. Go into the list of messages (assuming you have more
than one screen full of messages), press END,
then PGUP, arrow down TWICE, then press END
again. The screen messed up. Fixed.
52. If you had more than one column's worth of mail packets
on the screen, the mouse cursor would default to
the wrong position. Fixed.
53. If you had only one conference with mail in a mail
packet and you went to the conference list
screen, you never could return back to the
conference. Fixed.
54. If you tried to join a conference without messages after
reading a mail packet that did contain messages,
the screen would mess up. Fixed.
Thanks Brian Hillis
55. If you are a European user of 1stReader then this
release fixes the bug that restamps the date and
time of mail packets to TODAY. The fix requires
that you are using DOS 3.0 or higher. Before
the program goes out to get the date/time stamp
of the mail packet 1st switches to the US
country code in order to get the correct date
and time, then it switches back to YOUR country
code. It works here using DOS 5.0.
Thanks Alastair McIntyre
56. If you saved a message that spanned over two (or more)
messages, the reader wouldn't place a "Continued
in the next message..." on the bottom of the
messages. Nor would it place a counter inside
the subject field either. Fixed.
57. If you were in the file manager and had only one
column's worth of files and pressed the END
key on the keypad, the display would mess up.
Fixed.
Thanks Daniel Notowitz
58. The reader 'clipped' bulletin numbers past #99. In
other words, bulletin #110 would read as #11.
Also, changed bulletin #999 so that is reads as
"<conference> information" so the sysop can
place information about the conference in a
bulletin (BLT-1.999 for conf #1) if desired.
Thanks Greg Watson
59. If you used the ADD/DROP commands from the conference
join screen and then later went into the DOOR
configuration section in the 'read messages'
screen, you would loose your previous
adds/drops. Fixed.
60. 1stReader was creating zero byte sized REPLY files if
you used an external editor. This would cause
WordPerfect 5.0 to crash because it can't handle
a zero byte file. Fixed.
Thanks Scott Baker
61. If you used the /CALL command line switch and had left
files in the WORK subdirectory area, 1stReader
would ask you if you wish to resume reading the
mail packet. The reader now by-passes this
question and will clean the work area up
automatically.
62. This release of 1stReader uses RTLink 5.10. Previous
versions used RTLink 4.15 and were incompatible
with some EMMs running with Windows.
63. If you deleted a message in a folder the reader would
drop off the last message in the folder. Fixed.
Thanks Scott Baker
64. You can now press TAB and SHIFT+TAB when you are sitting
at the 'Personal' prompt when saving messages.
Thanks John Phillips
65. If you re-edited a message when no mail packets were on
file you would loose the conference number from
the original message. Fixed.
Thanks Doug Manne
66. Changed the way that 1stReader scans for ZIPPY searches.
The reader was looking at the entire 128 byte
message header for a match on the keywords. It
now only matches against the TO, FROM and
SUBJECT fields.
67. There was a problem in how 1stReader was counting
deleted messages in a folder. It would reset
the number of messages in the folder back to
400 messages each time you delete a message in
a folder.
Thanks David Pottier and John Phillips
68. You could not carbon copy a message if you tried to
carbon copy while editing a reply. Fixed.
Thanks John Phillips and Greg Watson
69. If you had multiple external editors in 1stReader and
decided to press the ESC key without entering
a message, the reader would still leave you at
the "Save this message" prompt. Fixed.
Thanks John Phillips
70. Ok, this time the CTRL+T keystroke in the internal
editor definitely is now fixed. CTRL+T lets you
delete one word at a time.
71. In the internal editor, if the cursor was positioned
underneath the last line of text, and you
pressed the Backspace key, the cursor would
move up one line, but it would be positioned at
the *beginning* of the line. It is now
correctly positioned at the end of the line.
Thanks Glenda Moore
72. If you used the Doorway mode in the terminal section
and then exited Doorway mode, the display would
be locked at line #17 instead of #24. Fixed.
73. 1stReader was not handling 'mangled' mail packets that
had been read by EZ-Reader. Fixed.
Thanks Tony Elliott
74. If you tried to unpack a zipped file using the "Unpack"
command in the file manager the reader would not
truncate the spaces that were appended to the
end of the subdirectory location. Fixed.
75. If you were viewing an ANSI reply and deleted it, the
reader failed to redisplay the 'message' screen
listing the commands on the bottom of the
screen. Fixed.
Thanks Scott Baker
76. If you used the '/TIME:' command line switch and passed
it a time without using a colon as the
hours:minutes seperator, (example: /TIME: 1800)
then the reader would immediately call the system
rather than waiting. Fixed.
